chore(deps): bump sharp from 0.34.5 to 0.35.0 - #252
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [sharp](https://github.com/lovell/sharp) from 0.34.5 to 0.35.0. - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.34.5...v0.35.0) --- updated-dependencies: - dependency-name: sharp dependency-version: 0.35.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
dependencies
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
cooperability
added a commit
that referenced
this pull request
Aug 26, 2026
Takes the repository from 53 known advisories to 5. All five that remain have no upstream fix: postcss (4) and sharp (1) are already at the latest published version, so nothing to move to. Resolves the substance of the open Dependabot PRs, which cannot themselves survive this branch -- they carry yarn.lock diffs and cannot rebase onto a tree with no yarn.lock. Direct bumps of note: - next 16.2.6 -> 16.2.11 (#254) - sharp 0.34.5 -> 0.35.3 (#252) - react / react-dom 19.1 -> 19.2.8, @types to match - @serwist/build 9.2.1 -> 9.5.12 (#213) - jest-environment-jsdom 30.2.0 -> 30.4.1 (#215) - postcss 8.5.10 -> 8.5.26 (#257), @babel/core (#241), and the rest of the patch-updates group (#265) via in-range `pnpm update` - @testing-library/jest-dom 6.6.3 -> 7.0.1. pnpm flagged 6.10.0 as a mis-published minor carrying breaking changes; 7.x is the clean line and its @testing-library/dom peer range is already satisfied. Transitive advisories (nanoid #264, brace-expansion #259, fast-uri #258, js-yaml #256, ws #247, form-data #236, tar #229 (the one CRITICAL), minimatch #228, follow-redirects #222) were resolved by letting `pnpm update` move the parents that pin them, rather than by pinning each child directly. That distinction is the point of the one override this adds: socks: ^2.8.9 ip-address had two advisories. The chain is socks -> ip-address, and socks 2.8.5 pins `ip-address: ^9`. Overriding ip-address to ^10 would have handed socks an API it does not expect -- precisely the failure that killed coverage when the inherited glob override reached test-exclude@6. socks 2.8.9 already declares `ip-address: ^10.1.1`, so bumping the parent lets the fixed child arrive legitimately. Fix the package that declares the bad range, not the package named in the advisory. Also drops @eslint/compat and @eslint/eslintrc, which became dead when the FlatCompat layer was removed, and annotates one more real `react-hooks/set-state-in-effect` hit that eslint-plugin-react-hooks 7.1 newly detects in PromptComposer. Like the OpioidConverter one it is described rather than fixed: it changes when a user's manual edits are discarded, and the component has no test coverage. NOT included, deliberately: tailwindcss 3 -> 4 (#214). That is a real migration -- a new config format and a rewritten cascade layer model -- with visual consequences on every page, and it belongs in its own PR with a human looking at the result. Verified: lint clean, typecheck clean, 4/4 tests with coverage, production build 14.2s. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013RtsQWaEaAe4iVnSoUCDfY
Contributor
Author
|
Superseded by #275. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps sharp from 0.34.5 to 0.35.0.
Release notes
Sourced from sharp's releases.
... (truncated)
Commits
2ed5af4Release v0.35.04475cf1Tests: update locator hash for sharp-libvips v1.3.0deb22ddUpgrade to sharp-libvips v1.3.007f1be9Prerelease v0.35.0-rc.8df1109bPrerelease v0.35.0-rc.7aca49b3Upgrade to libvips v8.18.3e9e86f5Type-check density option before range validation (#4536)2f0bcf0Docs: update supported image formats98e03b8Revert "Guard heif bitdepth property for prebuilt binaries"e4ea2f3CI: Ignore package minimum age in smoke testsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.